home *** CD-ROM | disk | FTP | other *** search
- '\"
- '\" Copyright 1992 Regents of the University of California
- '\" Permission to use, copy, modify, and distribute this
- '\" documentation for any purpose and without fee is hereby
- '\" granted, provided that this notice appears in all copies.
- '\" The University of California makes no representations about
- '\" the suitability of this material for any purpose. It is
- '\" provided "as is" without express or implied warranty.
- '\"
- '\" $Header: /user6/ouster/wish/man/RCS/grab.man,v 1.4 92/08/07 08:57:20 ouster Exp $ SPRITE (Berkeley)
- '/"
- .\" The definitions below are for supplemental macros used in Sprite
- .\" manual entries.
- .\"
- .\" .HS name section [date [version]]
- .\" Replacement for .TH in other man pages. See below for valid
- .\" section names.
- .\"
- .\" .AP type name in/out [indent]
- .\" Start paragraph describing an argument to a library procedure.
- .\" type is type of argument (int, etc.), in/out is either "in", "out",
- .\" or "in/out" to describe whether procedure reads or modifies arg,
- .\" and indent is equivalent to second arg of .IP (shouldn't ever be
- .\" needed; use .AS below instead)
- .\"
- .\" .AS [type [name]]
- .\" Give maximum sizes of arguments for setting tab stops. Type and
- .\" name are examples of largest possible arguments that will be passed
- .\" to .AP later. If args are omitted, default tab stops are used.
- .\"
- .\" .BS
- .\" Start box enclosure. From here until next .BE, everything will be
- .\" enclosed in one large box.
- .\"
- .\" .BE
- .\" End of box enclosure.
- .\"
- .\" .VS
- .\" Begin vertical sidebar, for use in marking newly-changed parts
- .\" of man pages.
- .\"
- .\" .VE
- .\" End of vertical sidebar.
- .\"
- .\" .DS
- .\" Begin an indented unfilled display.
- .\"
- .\" .DE
- .\" End of indented unfilled display.
- .\"
- '\" # Heading for Sprite man pages
- .de HS
- .if '\\$2'cmds' .TH \\$1 1 \\$3 \\$4
- .if '\\$2'lib' .TH \\$1 3 \\$3 \\$4
- .if '\\$2'tcl' .TH \\$1 3 \\$3 \\$4
- .if '\\$2'tk' .TH \\$1 3 \\$3 \\$4
- .if t .wh -1.3i ^B
- .nr ^l \\n(.l
- .ad b
- ..
- '\" # Start an argument description
- .de AP
- .ie !"\\$4"" .TP \\$4
- .el \{\
- . ie !"\\$2"" .TP \\n()Cu
- . el .TP 15
- .\}
- .ie !"\\$3"" \{\
- .ta \\n()Au \\n()Bu
- \&\\$1 \\fI\\$2\\fP (\\$3)
- .\".b
- .\}
- .el \{\
- .br
- .ie !"\\$2"" \{\
- \&\\$1 \\fI\\$2\\fP
- .\}
- .el \{\
- \&\\fI\\$1\\fP
- .\}
- .\}
- ..
- '\" # define tabbing values for .AP
- .de AS
- .nr )A 10n
- .if !"\\$1"" .nr )A \\w'\\$1'u+3n
- .nr )B \\n()Au+15n
- .\"
- .if !"\\$2"" .nr )B \\w'\\$2'u+\\n()Au+3n
- .nr )C \\n()Bu+\\w'(in/out)'u+2n
- ..
- '\" # BS - start boxed text
- '\" # ^y = starting y location
- '\" # ^b = 1
- .de BS
- .br
- .mk ^y
- .nr ^b 1u
- .if n .nf
- .if n .ti 0
- .if n \l'\\n(.lu\(ul'
- .if n .fi
- ..
- '\" # BE - end boxed text (draw box now)
- .de BE
- .nf
- .ti 0
- .mk ^t
- .ie n \l'\\n(^lu\(ul'
- .el \{\
- .\" Draw four-sided box normally, but don't draw top of
- .\" box if the box started on an earlier page.
- .ie !\\n(^b-1 \{\
- \h'-1.5n'\L'|\\n(^yu-1v'\l'\\n(^lu+3n\(ul'\L'\\n(^tu+1v-\\n(^yu'\l'|0u-1.5n\(ul'
- .\}
- .el \}\
- \h'-1.5n'\L'|\\n(^yu-1v'\h'\\n(^lu+3n'\L'\\n(^tu+1v-\\n(^yu'\l'|0u-1.5n\(ul'
- .\}
- .\}
- .fi
- .br
- .nr ^b 0
- ..
- '\" # VS - start vertical sidebar
- '\" # ^Y = starting y location
- '\" # ^v = 1 (for troff; for nroff this doesn't matter)
- .de VS
- .mk ^Y
- .ie n 'mc \s12\(br\s0
- .el .nr ^v 1u
- ..
- '\" # VE - end of vertical sidebar
- .de VE
- .ie n 'mc
- .el \{\
- .ev 2
- .nf
- .ti 0
- .mk ^t
- \h'|\\n(^lu+3n'\L'|\\n(^Yu-1v\(bv'\v'\\n(^tu+1v-\\n(^Yu'\h'-|\\n(^lu+3n'
- .sp -1
- .fi
- .ev
- .\}
- .nr ^v 0
- ..
- '\" # Special macro to handle page bottom: finish off current
- '\" # box/sidebar if in box/sidebar mode, then invoked standard
- '\" # page bottom macro.
- .de ^B
- .ev 2
- 'ti 0
- 'nf
- .mk ^t
- .if \\n(^b \{\
- .\" Draw three-sided box if this is the box's first page,
- .\" draw two sides but no top otherwise.
- .ie !\\n(^b-1 \h'-1.5n'\L'|\\n(^yu-1v'\l'\\n(^lu+3n\(ul'\L'\\n(^tu+1v-\\n(^yu'\h'|0u'\c
- .el \h'-1.5n'\L'|\\n(^yu-1v'\h'\\n(^lu+3n'\L'\\n(^tu+1v-\\n(^yu'\h'|0u'\c
- .\}
- .if \\n(^v \{\
- .nr ^x \\n(^tu+1v-\\n(^Yu
- \kx\h'-\\nxu'\h'|\\n(^lu+3n'\ky\L'-\\n(^xu'\v'\\n(^xu'\h'|0u'\c
- .\}
- .bp
- 'fi
- .ev
- .if \\n(^b \{\
- .mk ^y
- .nr ^b 2
- .\}
- .if \\n(^v \{\
- .mk ^Y
- .\}
- ..
- '\" # DS - begin display
- .de DS
- .RS
- .nf
- .sp
- ..
- '\" # DE - end display
- .de DE
- .fi
- .RE
- .sp .5
- ..
- .HS grab cmds
- .BS
- '\" Note: do not modify the .SH NAME line immediately below!
- .SH NAME
- grab \- Confine pointer and keyboard events to a particular window sub-tree
- .SH SYNOPSIS
- \fBgrab\fR
- .br
- \fBgrab \fIwindow\fR
- .br
- \fBgrab \fB\-global \fIwindow\fR
- .BE
-
- .SH DESCRIPTION
- .PP
- This command implements simple pointer and keyboard grabs for Tk.
- If the \fIwindow\fR argument is specified, then the pointer and keyboard
- are grabbed to that window as described below.
- If a grab is already in effect for another window in this
- application then the existing grab is automatically released.
- If a grab is already in effect for another application then
- an error is returned.
- If the \fIwindow\fR argument is specified as an empty string
- or as \fBnone\fR then any existing grab in the application is
- released.
- In all of the above cases an empty string is returned.
- If \fBgrab\fR is invoked with no arguments then the path name of
- the current grab window is returned, or \fBnone\fR if no grab
- is active in this application.
- .PP
- Tk's grabs are somewhat different than the grabs
- described in the Xlib documentation.
- A Tk grab simply restricts all pointer events to the window tree
- rooted at \fIwindow\fR.
- Whenever the pointer is within \fIwindow\fR's subtree, the pointer
- will behave exactly the same as if there had been no grab at all
- and all events will be reported in the normal fashion.
- When the pointer is outside \fIwindow\fR's tree, button presses and
- releases and
- mouse motion events are reported to \fIwindow\fR, and window entry
- and window exit events are ignored.
- The grab subtree ``owns'' the pointer:
- windows outside the grab subtree will be visible on the screen
- but they will be totally insensitive until the grab is released.
- The tree of windows underneath \fIwindow\fR can include top-level
- windows.
- If this is the case, then all of those top-level windows
- and their descendants will continue to receive mouse events
- during the grab.
- .PP
- Two forms of grabs are possible: local and global.
- A local grab affects only the grabbing application: events will
- be reported to other applications as if the grab had never occurred.
- Grabs are local by default.
- A global grab is requested with the \fB\-global\fR switch.
- In this case the grab will lock out all applications on the screen,
- so that only the given subtree of the grabbing application will be
- sensitive to pointer events.
- During global grabs the window manager will not receive pointer
- events either.
- .PP
- During local grabs, keyboard events are handled as usual: the window
- manager controls which application receives keyboard events, and
- if they are sent to any window in the grabbing application then they are
- redirected to the focus window.
- During a global grab Tk grabs the keyboard so that all keyboard events
- are always sent to the grabbing application.
- The \fBfocus\fR command is still used to determine which window in the
- application receives the keyboard events.
- The keyboard grab is released when the grab is released.
- .PP
- Grabs apply to particular displays. If an application has windows
- on multiple displays, then it can establish a separate grab on each
- display.
- The grab on a particular display affects only the windows on
- that display.
- .PP
- Pointer events include mouse button presses, mouse button releases,
- pointer motions, window entries, and window exits.
- Keyboard events include key presses and key releases.
-
- .SH BUGS
- .PP
- If \fBgrab\fR is invoked several times in a row with different
- \fIwindow\fR arguments and insufficient time to process all pending
- events between the invocations, then the grab-related events may
- end up in the wrong order in the event queue. This problem is
- mostly likely to occur with local grabs. The solution is to insert
- \fBafter\fR commands between the \fBgrab\fR invocations, so that
- there's enough time to clear the event queue before the next
- \fBgrab\fR invocation.
- .PP
- It took an incredibly complex and gross implementation to produce
- the simple grab effect described above.
- Given the current implementation, it isn't safe for applications
- to use the Xlib grab facilities at all except through the Tk grab
- procedures.
- If applications try to manipulate X's grab mechanisms directly,
- things will probably break.
-
- .SH KEYWORDS
- grab, variable, wait, window
-